Skip to content

glossary: improve and normalize technical Japanese terms#32

Open
yahonda wants to merge 1 commit into
pingcap:mainfrom
yahonda:fix-glossary-terms-normalization
Open

glossary: improve and normalize technical Japanese terms#32
yahonda wants to merge 1 commit into
pingcap:mainfrom
yahonda:fix-glossary-terms-normalization

Conversation

@yahonda
Copy link
Copy Markdown
Member

@yahonda yahonda commented May 22, 2026

Description

This PR improves the Japanese glossary to ensure more natural and consistent technical terms in the machine-translated documentation, focusing on high-impact terms with minimal risk of side effects.

Key Changes

  • Normalization of standard terms:
    • Updated Cluster to クラスター (standard Katakana with long vowel mark).
    • Updated Configuration to 設定 (more idiomatic than コンフィグレーション).
    • Improved phrasing for Multiple Data Centers in One City Deployment.
  • Protection of product and technical names:
    • Added Self-Managed to prevent translation into Katakana, preserving its role as part of the product name.
    • Added protection for 2xlarge through 16xlarge instance types (consistent with the existing xlarge entry) to prevent over-translation in instance type tables.
  • Avoidance of literal translations:
    • Normalized Hotspot to ホットスポット to prevent literal translations like "熱い地点".
    • Normalized Primary Cluster and Secondary Cluster phrasing.

These entries have been carefully selected to avoid conflicts with common configuration keys or code snippets while significantly improving the readability of core documentation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant